SUPPORT / SAMPLES & SAS NOTES
 

Support

Problem Note 47267: The METALIB procedure might end abnormally when you use it to update tables in a library that contain a SAS® Data Integration Studio work table

DetailsAboutRate It

When you use the METALIB procedure in SAS® 9.2 or SAS® 9.3 to update tables in a library that contains a SAS® Data Integration Studio work table, the procedure might terminate abnormally. The errors that you receive can vary, as described below.

  • The following error message appears in SAS® 9.2 if the TL= option (the tracing–level option) is not included in the PROC METALIB statement. This error also occurs in SAS® 9.3, regardless of the presence of the TL= option:
    ERROR: No metadata objects found matching the specified URI.
  • Along with the previous error, the following error also occurs in SAS 9.3:

    ERROR: PhysicalTable : . cannot be found in the ptable container in the Foundation repository.
  • The following error occurs in SAS 9.2 when you do include the TL= option in the PROC METALIB statement:
    ERROR: Invalid value for the. . .

    The error shown above is followed by several pages of garbled text and unprintable characters, as illustrated here:

    image label

  • This problem occurs when the properties for a work table in SAS Data Integration Studio are modified to permanently store the work table in the library that PROC METALIB is attempting to update. The presence of this WorkTable object in the SAS® Metadata Repository prevents PROC METALIB from updating the tables that are contained within the library.

    You can determine easily whether you have WorkTable objects stored in your library by using the METABROWSE tool in Foundation SAS® software.

    1. Invoke the tool by entering metabrowse in the command box of the SAS session.
    2. At the prompt, provide the appropriate information that is necessary to connect to your SAS Metadata Server.
    3. Expand the repository (for example, Foundation) that contains your library.
    4. Expand the SASLibrary object type. Then locate your library and expand it.
    5. Click the Tables association to see a list of tables in the right pane. The Type column shows the type of the table. All of the traditional table objects have a type value of PhysicalTable, whereas any table that causes the errors mentioned previously have a type value of WorkTable, as shown in the following display:

      image label

    To circumvent the problem, update the job in SAS Data Integration Studio and define the work table that you want to store in a temporary library rather than in the permanent library that is registered in metadata. Then delete the work table from the permanent library using the Data Library Manager plug-in within SAS® Management Console.



    Operating System and Release Information

    Product FamilyProductSystemProduct ReleaseSAS Release
    ReportedFixed*ReportedFixed*
    SAS SystemBase SASz/OS9.21_M39.3_M19.2 TS2M39.3 TS1M1
    Microsoft® Windows® for 64-Bit Itanium-based Systems9.21_M39.3_M19.2 TS2M39.3 TS1M1
    Microsoft Windows Server 2003 Datacenter 64-bit Edition9.21_M39.3_M19.2 TS2M39.3 TS1M1
    Microsoft Windows Server 2003 Enterprise 64-bit Edition9.21_M39.3_M19.2 TS2M39.3 TS1M1
    Microsoft Windows XP 64-bit Edition9.21_M39.3_M19.2 TS2M39.3 TS1M1
    Microsoft® Windows® for x649.21_M39.3_M19.2 TS2M39.3 TS1M1
    Microsoft Windows Server 2003 Datacenter Edition9.21_M39.3_M19.2 TS2M39.3 TS1M1
    Microsoft Windows Server 2003 Enterprise Edition9.21_M39.3_M19.2 TS2M39.3 TS1M1
    Microsoft Windows Server 2003 Standard Edition9.21_M39.3_M19.2 TS2M39.3 TS1M1
    Microsoft Windows Server 2003 for x649.21_M39.3_M19.2 TS2M39.3 TS1M1
    Microsoft Windows Server 20089.21_M39.3_M19.2 TS2M39.3 TS1M1
    Microsoft Windows Server 2008 for x649.21_M39.3_M19.2 TS2M39.3 TS1M1
    Microsoft Windows XP Professional9.21_M39.3_M19.2 TS2M39.3 TS1M1
    Windows 7 Enterprise 32 bit9.21_M39.3_M19.2 TS2M39.3 TS1M1
    Windows 7 Enterprise x649.21_M39.3_M19.2 TS2M39.3 TS1M1
    Windows 7 Home Premium 32 bit9.21_M39.3_M19.2 TS2M39.3 TS1M1
    Windows 7 Home Premium x649.21_M39.3_M19.2 TS2M39.3 TS1M1
    Windows 7 Professional 32 bit9.21_M39.3_M19.2 TS2M39.3 TS1M1
    Windows 7 Professional x649.21_M39.3_M19.2 TS2M39.3 TS1M1
    Windows 7 Ultimate 32 bit9.21_M39.3_M19.2 TS2M39.3 TS1M1
    Windows 7 Ultimate x649.21_M39.3_M19.2 TS2M39.3 TS1M1
    Windows Vista9.21_M39.3_M19.2 TS2M39.3 TS1M1
    Windows Vista for x649.21_M39.3_M19.2 TS2M39.3 TS1M1
    64-bit Enabled AIX9.21_M39.3_M19.2 TS2M39.3 TS1M1
    64-bit Enabled HP-UX9.21_M39.3_M19.2 TS2M39.3 TS1M1
    64-bit Enabled Solaris9.21_M39.3_M19.2 TS2M39.3 TS1M1
    HP-UX IPF9.21_M39.3_M19.2 TS2M39.3 TS1M1
    Linux9.21_M39.3_M19.2 TS2M39.3 TS1M1
    Linux for x649.21_M39.3_M19.2 TS2M39.3 TS1M1
    OpenVMS on HP Integrity9.21_M39.3_M19.2 TS2M39.3 TS1M1
    Solaris for x649.21_M39.3_M19.2 TS2M39.3 TS1M1
    * For software releases that are not yet generally available, the Fixed Release is the software release in which the problem is planned to be fixed.